home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20000824-20010305
/
000110_news@columbia.edu _Wed Nov 1 03:10:58 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@columbia.edu>
Received: from watsun.cc.columbia.edu (watsun.cc.columbia.edu [128.59.39.2])
by uhaligani.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id DAA08383
for <kermit.misc@cpunix.cc.columbia.edu>; Wed, 1 Nov 2000 03:10:54 -0500 (EST)
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id DAA11546
for <kermit.misc@watsun.cc.columbia.edu>; Wed, 1 Nov 2000 03:10:20 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.9.3/8.9.3) id CAA15059
for kermit.misc@watsun.cc.columbia.edu; Wed, 1 Nov 2000 02:53:25 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: "dls2" <dlshearer@home.com>
Subject: Re: Cumulative Packet Error Limit in Kermit??
Message-ID: <9ZPL5.97972$ib7.13838586@news1.rdc1.nj.home.com>
Date: Wed, 01 Nov 2000 07:52:37 GMT
Organization: @Home Network
To: kermit.misc@columbia.edu
"Grant Cartledge" <Grant.Cartledge@nec.com.au> wrote:
> We are using the Kermit protocol coded within the commercial package
> "Procomm Plus". Our application is a satellite communications system
> which uses mobile terminals in vehicles. Our current testing is
> concentrating on data transmission in adverse propagation conditions
> whereby the end-to-end link is interrupted by line-of-sight obstructions
> (in this case, trees). The periods of shading obvioulsy cause lost and
> errored packets. The file transfer is failing by exceeding a cumulative
> error limit. This surprised us as prior testing (albeit in slightly less
> shaded conditions) did not show this phenomenon. Is this error limit
> inherent in the Kermit protocol or is it an artificial limit imposed by
> the authors of Procomm Plus??
The choice to abort, after a set number of errors, is an implementation
issue, rather than a problem with the protocol, itself. Under conditions
of error, the Kermit protocol indicates that it just keeps resending, until
such time as proper acknowledgement is made, or, until a decision to
abort has been acted upon. The decision to abort is made by either a
person or a program, and, in this case, the decision to abort is made
by the program, Procomm Plus.
Also,
"On network connections (e.g. TCP/IP), it is usually best to turn off
flow control entirely, because the underlying networking method
supplies fully effective flow control."
http://www.columbia.edu/kermit/faq-c-zmo.html#faq-c-zmo
-- Derrick Shearer